Skip to content

Docs/sdk update documentation#303

Merged
GeWuYou merged 2 commits into
mainfrom
docs/sdk-update-documentation
Apr 29, 2026
Merged

Docs/sdk update documentation#303
GeWuYou merged 2 commits into
mainfrom
docs/sdk-update-documentation

Conversation

@GeWuYou

@GeWuYou GeWuYou commented Apr 29, 2026

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

发布说明

  • Documentation
    • 更新多个模块 README 文档,用类型/接口名称替代文件路径引用,提高文档清晰度
    • 优化中文文档导航文本和用户阅读指引,改进跨文档链接建议
    • 移除特定实现细节的引用,采用更通用的描述方式,增强文档可维护性

GeWuYou added 2 commits April 29, 2026 13:23
- 更新 Game / Godot 细页的交叉链接与边界描述,移除内部路径、旧文档对比和命令式跳转

- 更新 GFramework.Godot 与配置工具 README 的公开标签,避免暴露测试路径和原始文档路径

- 补充 documentation-full-coverage-governance 的 RP-049 恢复点、验证结果与 origin/main stop-condition 计量
- 更新 Game 数据与存储页面、Godot UI 页面中的 reader-facing 说明,移除内部证据口吻、外部项目指代和生硬导流

- 更新 CQRS 抽象层与 SourceGenerators.Common README 的标签表述,避免暴露源文件路径列表和实现级打包术语

- 补充 documentation-full-coverage-governance 的 RP-050 恢复点、验证结果与 origin/main stop-condition 计量
@coderabbitai

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6b22833f-7138-4fdf-b7a3-c98e376bdf37

📥 Commits

Reviewing files that changed from the base of the PR and between ddaabd8 and 1d5404e.

📒 Files selected for processing (18)
  • GFramework.Cqrs.Abstractions/README.md
  • GFramework.Godot/README.md
  • GFramework.SourceGenerators.Common/README.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/game/scene.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/godot/signal.md
  • docs/zh-CN/godot/storage.md
  • docs/zh-CN/godot/ui.md
  • tools/gframework-config-tool/README.md
📜 Recent review details
🧰 Additional context used
📓 Path-based instructions (7)
**/README.md

📄 CodeRabbit inference engine (AGENTS.md)

**/README.md: Use the canonical filename README.md for module documentation; do not introduce variants like ReadMe.md
A module README MUST describe: the module's purpose, relationship to adjacent runtime/abstractions/generator packages, major subdirectories or subsystems, minimum adoption path, and corresponding docs/zh-CN/ entry points
If a module's responsibilities, setup, public API surface, generator inputs, or adoption path change, update that module's README.md in the same change

Files:

  • tools/gframework-config-tool/README.md
  • GFramework.Godot/README.md
  • GFramework.SourceGenerators.Common/README.md
  • GFramework.Cqrs.Abstractions/README.md
docs/**/*.md

📄 CodeRabbit inference engine (CLAUDE.md)

Documentation should be organized with Chinese content in docs/zh-CN/ and structured to include getting started, module-specific capabilities (Core, Game, Godot, ECS), source generator usage, tutorials, best practices, and troubleshooting

Files:

  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/game/scene.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/godot/ui.md
  • docs/zh-CN/godot/storage.md
  • docs/zh-CN/godot/signal.md
{README.md,docs/**}

📄 CodeRabbit inference engine (AGENTS.md)

{README.md,docs/**}: Update the relevant README.md or docs/ page when behavior, setup steps, architecture guidance, or user-facing examples change
Public documentation MUST NOT include governance-only content such as inventory tables, coverage baselines, review queues, batch metrics, recovery points, trace summaries, or 'this still needs a later audit wave' notes
Public documentation MUST use semantic section titles and link labels; do not surface raw filenames or paths as reader-facing navigation text when a meaningful destination label is available
Public documentation MUST avoid rhetorical, self-referential, or AI-sounding headings and prompts; prefer neutral labels like '公开入口'、'模块与包关系'、'栏目覆盖范围' and '相关主题'
Public documentation MUST present limitations, suitability, and migration boundaries as adoption guidance; do not publish internal-governance or product-roadmap wording
Keep code samples, package names, and command examples aligned with the current repository state in documentation
Prefer documenting behavior and design intent, not only API surface in user documentation
When a public page references XML docs or API coverage, convert that evidence into reader-facing guidance by explaining which types/namespaces/entry points readers should inspect and why, instead of exposing audit counts or governance terminology
If an existing documentation page no longer reflects the current implementation, fixing the code without fixing the documentation is considered incomplete work
Do not rely on 'the code is self-explanatory' for framework features that consumers need to adopt; write the adoption path down so future users do not need to rediscover it from source
When examples are rewritten, preserve only the parts that remain true; delete or replace speculative examples instead of lightly editing them into another inaccurate form

Files:

  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/game/scene.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/godot/ui.md
  • docs/zh-CN/godot/storage.md
  • docs/zh-CN/godot/signal.md
docs/zh-CN/**

📄 CodeRabbit inference engine (AGENTS.md)

docs/zh-CN/**: When a feature is added, removed, renamed, or substantially refactored, contributors MUST update or create the corresponding user-facing integration documentation in docs/zh-CN/ in the same change
For integration-oriented features such as the AI-First config system, documentation MUST cover: project directory layout and file conventions, required project or package wiring, minimal working usage example, and migration or compatibility notes

Files:

  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/game/scene.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/godot/ui.md
  • docs/zh-CN/godot/storage.md
  • docs/zh-CN/godot/signal.md
docs/**

📄 CodeRabbit inference engine (AGENTS.md)

If a docs category appears in VitePress navigation or sidebar, it MUST have a real landing page or be removed from navigation in the same change

Files:

  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/game/scene.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/godot/ui.md
  • docs/zh-CN/godot/storage.md
  • docs/zh-CN/godot/signal.md
ai-plan/public/*/traces/**

📄 CodeRabbit inference engine (AGENTS.md)

Contributors MUST maintain a matching execution trace under ai-plan/public/<topic>/traces/ for complex work, recording the current date, key decisions, validation milestones, and the immediate next step

Files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
ai-plan/public/*/todos/**

📄 CodeRabbit inference engine (AGENTS.md)

ai-plan/public/*/todos/**: When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under ai-plan/public/<topic>/todos/ in the same change
Tracking updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point
Active tracking and trace files are recovery entrypoints, not append-only changelogs; they MUST stay concise enough for boot to locate the current recovery point quickly
Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely
When completed and validated stages begin to accumulate, contributors MUST archive their detailed history out of the active todos/ and traces/ entry files in the same change, keeping only the current recovery point, active facts, active risks, immediate next step, and pointers to archive files
When a task spans multiple commits or is likely to exceed a single agent context window, update both the recovery document and the trace at each meaningful milestone before pausing or handing work off
If subagents are used on a complex task, the main agent MUST capture the delegated scope and any accepted findings in the active recovery document or trace before continuing implementation

Files:

  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
🧠 Learnings (35)
📓 Common learnings
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-17T11:35:08.762Z
Learning: Applies to docs/**/*.md : Documentation should be organized with Chinese content in docs/zh-CN/ and structured to include getting started, module-specific capabilities (Core, Game, Godot, ECS), source generator usage, tutorials, best practices, and troubleshooting
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Public documentation MUST avoid rhetorical, self-referential, or AI-sounding headings and prompts; prefer neutral labels like '公开入口'、'模块与包关系'、'栏目覆盖范围' and '相关主题'
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Update the relevant `README.md` or `docs/` page when behavior, setup steps, architecture guidance, or user-facing examples change
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to docs/zh-CN/** : When a feature is added, removed, renamed, or substantially refactored, contributors MUST update or create the corresponding user-facing integration documentation in `docs/zh-CN/` in the same change

Applied to files:

  • tools/gframework-config-tool/README.md
  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to docs/zh-CN/** : For integration-oriented features such as the AI-First config system, documentation MUST cover: project directory layout and file conventions, required project or package wiring, minimal working usage example, and migration or compatibility notes

Applied to files:

  • tools/gframework-config-tool/README.md
  • docs/zh-CN/ecs/arch.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/godot/ui.md
  • docs/zh-CN/godot/storage.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Public documentation MUST avoid rhetorical, self-referential, or AI-sounding headings and prompts; prefer neutral labels like '公开入口'、'模块与包关系'、'栏目覆盖范围' and '相关主题'

Applied to files:

  • tools/gframework-config-tool/README.md
  • docs/zh-CN/game/data.md
  • docs/zh-CN/godot/index.md
  • docs/zh-CN/game/storage.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/game/config-system.md
  • docs/zh-CN/godot/ui.md
  • docs/zh-CN/godot/storage.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Update the relevant `README.md` or `docs/` page when behavior, setup steps, architecture guidance, or user-facing examples change

Applied to files:

  • tools/gframework-config-tool/README.md
  • docs/zh-CN/godot/setting.md
  • GFramework.Cqrs.Abstractions/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : When a public page references XML docs or API coverage, convert that evidence into reader-facing guidance by explaining which types/namespaces/entry points readers should inspect and why, instead of exposing audit counts or governance terminology

Applied to files:

  • tools/gframework-config-tool/README.md
  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/README.md : A module README MUST describe: the module's purpose, relationship to adjacent runtime/abstractions/generator packages, major subdirectories or subsystems, minimum adoption path, and corresponding `docs/zh-CN/` entry points

Applied to files:

  • tools/gframework-config-tool/README.md
  • docs/zh-CN/game/data.md
  • GFramework.SourceGenerators.Common/README.md
  • GFramework.Cqrs.Abstractions/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Public documentation MUST present limitations, suitability, and migration boundaries as adoption guidance; do not publish internal-governance or product-roadmap wording

Applied to files:

  • tools/gframework-config-tool/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Public documentation MUST use semantic section titles and link labels; do not surface raw filenames or paths as reader-facing navigation text when a meaningful destination label is available

Applied to files:

  • tools/gframework-config-tool/README.md
📚 Learning: 2026-04-17T11:35:08.762Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-17T11:35:08.762Z
Learning: Applies to docs/**/*.md : Documentation should be organized with Chinese content in docs/zh-CN/ and structured to include getting started, module-specific capabilities (Core, Game, Godot, ECS), source generator usage, tutorials, best practices, and troubleshooting

Applied to files:

  • tools/gframework-config-tool/README.md
  • docs/zh-CN/godot/logging.md
  • docs/zh-CN/core/index.md
  • docs/zh-CN/godot/setting.md
  • docs/zh-CN/godot/storage.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/README.md : If a module's responsibilities, setup, public API surface, generator inputs, or adoption path change, update that module's `README.md` in the same change

Applied to files:

  • tools/gframework-config-tool/README.md
  • GFramework.Godot/README.md
  • GFramework.SourceGenerators.Common/README.md
  • GFramework.Cqrs.Abstractions/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: The main documentation site lives under `docs/`, with Chinese content under `docs/zh-CN/`

Applied to files:

  • tools/gframework-config-tool/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.cs : Any change to public API, lifecycle semantics, module behavior, or extension points MUST update the related XML docs

Applied to files:

  • GFramework.Godot/README.md
  • GFramework.SourceGenerators.Common/README.md
  • GFramework.Cqrs.Abstractions/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.Tests.cs : Reuse existing architecture test infrastructure when relevant: `ArchitectureTestsBase<T>`, `SyncTestArchitecture`, `AsyncTestArchitecture`

Applied to files:

  • GFramework.Godot/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.cs : Source generator changes MUST be covered by generator tests

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.cs : Keep source generators deterministic and free of hidden environment or network dependencies

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Every user-facing package or module directory that contains a `*.csproj` intended for direct consumption MUST have a sibling `README.md`

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-16T13:26:01.780Z
Learnt from: GeWuYou
Repo: GeWuYou/GFramework PR: 235
File: GFramework.SourceGenerators.Tests/Rule/ContextAwareGeneratorSnapshotTests.cs:1-3
Timestamp: 2026-04-16T13:26:01.780Z
Learning: In the GeWuYou/GFramework repository, the test project `GFramework.SourceGenerators.Tests` provides `global using NUnit.Framework;` via its `GlobalUsings.cs`. Do not flag missing `using NUnit.Framework;` directives in test files within this project, as the global using already covers it. The project-wide GlobalUsings.cs pattern is used broadly to supply common namespaces (including NUnit, System.IO, etc.) without per-file imports.

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.cs : When generator behavior changes intentionally, update snapshots together with the implementation

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-06T12:45:47.739Z
Learnt from: GeWuYou
Repo: GeWuYou/GFramework PR: 190
File: GFramework.Game/Config/GameConfigBootstrap.cs:1-3
Timestamp: 2026-04-06T12:45:47.739Z
Learning: In the GFramework repository (GeWuYou/GFramework), even though `ImplicitUsings` is disabled in the `.csproj` files, the project uses a manual `GlobalUsings.cs` file with `global using` directives to provide common System namespaces (e.g., System, System.Threading, System.Threading.Tasks) project-wide. Do not flag missing System-level `using` imports in C# files within this repository, as they are covered by GlobalUsings.cs.

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.csproj : Minimize new package dependencies and add them only when necessary with narrow scope

Applied to files:

  • GFramework.SourceGenerators.Common/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/traces/** : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work, recording the current date, key decisions, validation milestones, and the immediate next step

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to {README.md,docs/**} : Public documentation MUST NOT include governance-only content such as inventory tables, coverage baselines, review queues, batch metrics, recovery points, trace summaries, or 'this still needs a later audit wave' notes

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Governance-only material such as XML audit snapshots, documentation remediation baselines, backlog status, and recovery metadata belongs in `ai-plan/**`, not in public docs

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/todos/** : Tracking updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/todos/** : When a task spans multiple commits or is likely to exceed a single agent context window, update both the recovery document and the trace at each meaningful milestone before pausing or handing work off

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/todos/** : Active tracking and trace files are recovery entrypoints, not append-only changelogs; they MUST stay concise enough for `boot` to locate the current recovery point quickly

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/todos/** : When completed and validated stages begin to accumulate, contributors MUST archive their detailed history out of the active `todos/` and `traces/` entry files in the same change, keeping only the current recovery point, active facts, active risks, immediate next step, and pointers to archive files

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/README.md : When a worktree-to-topic mapping changes, or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-17T11:35:08.762Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-17T11:35:08.762Z
Learning: Applies to **/Cqrs/**/*.cs : Use CQRS (Command Query Responsibility Segregation) pattern with the Cqrs naming entry point instead of the historical Mediator alias

Applied to files:

  • GFramework.Cqrs.Abstractions/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.cs : If a framework abstraction changes meaning or intended usage, update the explanatory comments in code as part of the same change

Applied to files:

  • GFramework.Cqrs.Abstractions/README.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/todos/** : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to ai-plan/public/*/todos/** : Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
📚 Learning: 2026-04-26T03:16:48.230Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-26T03:16:48.230Z
Learning: Applies to **/*.csproj : Follow repository defaults: `ImplicitUsings` disabled, `Nullable` enabled, `GenerateDocumentationFile` enabled for shipped libraries, `LangVersion` generally `preview` in main libraries

Applied to files:

  • ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md
🪛 LanguageTool
docs/zh-CN/godot/ui.md

[uncategorized] ~300-~300: 动词的修饰一般为‘形容词(副词)+地+动词’。您的意思是否是:强"地"输入
Context: ...义 如果页面只实现 IUiPage,它只有基础生命周期。 如果还需要更强的输入仲裁或暂停语义,可以继续实现: - `IUiInteractionProf...

(wb4)

ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md

[grammar] ~10-~10: Ensure spelling is correct
Context: ...ata.mdgame/storage.mdgodot/ui.mdGFramework.Cqrs.Abstractions/README.mdGFramework.Sou...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~50-~50: Ensure spelling is correct
Context: ...写示例。 - explorer 给出的 GFramework.Cqrs / GFramework.Cqrs.Abstractions README 源文件列表问题先不纳入本轮,因为那已...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md

[grammar] ~22-~22: Ensure spelling is correct
Context: ...a.mdgame/storage.mdgodot/ui.mdGFramework.Cqrs.Abstractions/README.mdGFramework.Sou...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~29-~29: Ensure spelling is correct
Context: ...a.mdgame/storage.mdgodot/ui.mdGFramework.Cqrs.Abstractions/README.mdGFramework.Sou...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~29-~29: Ensure spelling is correct
Context: ...前的做法”“优先看” 这类内部或生硬口吻,并把 CQRS 抽象层 README 的源文件列表改成契约类型族说明。 - 2026-04-29 新一轮 batch boot 已收口 `docs/zh-CN/godot/storag...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~73-~73: Ensure spelling is correct
Context: ...路径重写,review 面会明显扩大。 - GFramework.CqrsGFramework.Cqrs.SourceGenerators、`GFramework.Game.Sour...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (22)
docs/zh-CN/godot/logging.md (1)

162-163: 这处读者引导改写是正确的。

从“边界声明”改为“继续阅读 Core 日志系统的 provider 组合方式”,既保留限制说明,也提供了可执行迁移路径;链接标签是语义化文案,符合公开文档导航规范。

As per coding guidelines "Public documentation MUST use semantic section titles and link labels; do not surface raw filenames or paths as reader-facing navigation text when a meaningful destination label is available".

docs/zh-CN/godot/signal.md (1)

142-142: 边界与迁移表述更新合理,读者导向更清晰。

Line 142 和 Line 146 的改动把“互补关系”和“公开入口边界”讲清楚了,避免了强制迁移顺序的误导,也更符合接入指导语气。

As per coding guidelines "Public documentation MUST present limitations, suitability, and migration boundaries as adoption guidance; do not publish internal-governance or product-roadmap wording".

Also applies to: 146-146

docs/zh-CN/godot/index.md (1)

143-143: 措辞调整合理,导航语义更中性。

该处改为“可继续阅读”后,读者引导更自然,且不影响后续链接可达性。

docs/zh-CN/core/index.md (1)

135-137: 改动方向正确,跨模块导读更统一。

该段链接文案统一后,与页面其余“继续阅读”风格保持一致,可读性更好。

docs/zh-CN/game/data.md (1)

19-19: 文案微调恰当,保持了原有技术语义。

这两处修改提升了阅读流畅度,同时没有改变仓库分工与行为说明。

Also applies to: 86-86

docs/zh-CN/game/config-system.md (1)

439-439: 表述更直接,能力边界依然清晰。

该句改写后可读性更高,且未放宽查询辅助的生成条件。

docs/zh-CN/game/storage.md (1)

153-153: 分层定位更清楚,导读语气更友好。

该处把“底层能力”和“业务入口”区分得更明确,读者更不易误解 IStorage 的定位。

Also applies to: 164-165

docs/zh-CN/godot/setting.md (1)

136-139: 小节命名与导读表述改得很好。

标题更语义化,且“可继续阅读”式跳转提示更符合公开文档阅读体验。

Also applies to: 141-144

docs/zh-CN/godot/storage.md (1)

110-112: 导读语气统一,跨页引用保持清晰。

该处改动提升了页面间导航的一致性,没有引入信息损失。

Also applies to: 121-122

docs/zh-CN/game/scene.md (2)

162-163: 文档改进得当!

此处将实现指导从具体路径引用改为通用的接口契约说明,符合公开文档的标准。修订后的表述更加项目中立,避免了暴露内部实现路径,使读者能专注于 ISceneRoot 契约本身的职责边界。


1-262: 整体文档结构符合规范

文档组织良好,符合所有适用的编码准则:

  • 使用语义化章节标题("当前公开入口"、"推荐阅读"等中性标签)
  • 链接使用有意义的目标标签,未暴露原始文件路径
  • 无治理专用内容(如库存表、覆盖率基线、恢复点等)
  • 内容聚焦于采纳指导和契约说明,适合公开发布
tools/gframework-config-tool/README.md (1)

94-95: 文档链接标签改进符合规范。

将链接显示文本从文件路径改为语义化的中文标签("Game 配置工具"、"Game 配置系统"),提升了文档的可读性和用户友好度。符合编码规范要求:"公开文档必须使用语义化的章节标题和链接标签;当有意义的目标标签可用时,不应将原始文件名或路径作为面向读者的导航文本。"

docs/zh-CN/ecs/arch.md (1)

128-128: 移除内部文档对比参考,符合规范。

删除了"排除旧文档推断"这类内部治理性质的句式,保留了建议读者参考源码 XML 注释和实现行为的实用指导。符合编码规范:"公开文档不得包含治理性内容,如库存表、覆盖基线、审查队列、批处理指标、恢复点、追踪摘要或'这仍需后续审计'的注释。"

GFramework.SourceGenerators.Common/README.md (1)

28-29: 实现术语改为采用指导,提升可读性。

将具体的实现标志 IsPackable=false 改为更通用的面向读者说明"不会单独作为消费包提供",使文档更关注用户需求而非内部实现细节。符合编码规范:"公开文档必须将限制、适用性和迁移边界呈现为采用指导;不要发布内部治理或产品路线图措辞。"

GFramework.Godot/README.md (1)

105-105: 移除测试文件路径引用,保留行为说明。

将具体的测试文件路径替换为通用的"已有测试覆盖"说明,同时保留了关键行为描述(锚点缺失时抛出 InvalidOperationException)。这样既避免了暴露内部测试结构,又为读者提供了必要的行为契约信息。符合编码规范的语义化导航要求。

docs/zh-CN/godot/ui.md (4)

41-42: 明确 UI 页面集成要求,改进措辞。

强调实例化节点必须显式提供 GetPage() 或使用 [AutoUiPage] 生成样板,使集成要求更加清晰。措辞从内部实现描述改为面向读者的集成指导,提升了文档的实用性。


138-138: 移除特定项目引用,使用通用说明。

将 "CoreGrid"-specific 的表述改为"项目侧常见的 UiRoot 接法",使文档更具通用性和适用性。避免了将内部示例项目当作唯一参考的误导。


224-224: 标准化生成器集成说明。

[AutoUiPage] 的描述改为更标准的集成措辞"更常见的接法",保持了技术准确性的同时提升了表达的自然度。


300-300: 简化输入仲裁说明,保留核心接口。

移除了特定项目(CoreGrid)引用,直接列出相关接口(IUiInteractionProfileProviderIUiActionHandler),使说明更聚焦于框架契约本身。

GFramework.Cqrs.Abstractions/README.md (1)

33-41: 用契约类型替换文件路径,大幅提升可读性。

"子系统地图"部分从列举源文件路径(如 Cqrs/...)改为列举公开契约类型(如 IRequest<TResponse>IRequestHandler<,> 等)。这使得文档真正面向使用者,读者可以直接了解可用的接口和类型,而不需要关心内部文件组织结构。完全符合编码规范:"公开文档必须使用语义化的章节标题和链接标签;当有意义的目标标签可用时,不应将原始文件名或路径作为面向读者的导航文本。"

ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md (1)

15-24: 治理跟踪文档更新规范。

按照编码规范要求更新了跟踪文档:

  • 明确记录了当前恢复点 RP-050
  • 详细记录了验证结果(包括具体的验证命令和通过状态)
  • 更新了当前状态摘要、风险和下一步行动
  • 正确反映了已完成工作、新发现的问题和下一个推荐的恢复点

符合规范:"在按跟踪实施计划工作时,贡献者必须在同一变更中更新 ai-plan/public/<topic>/todos/ 下的相应跟踪文档。跟踪更新必须反映已完成的工作、新发现的问题、验证结果和下一个推荐的恢复点。"

Also applies to: 93-103

ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md (1)

3-77: 执行追踪记录完整规范。

新增的追踪条目正确记录了复杂工作的关键信息:

  • 当前日期:2026-04-29
  • 恢复点标识:RP-049 和 RP-050
  • 关键决策:包括批处理范围、stop condition、文档修改策略等
  • 验证里程碑:详细的验证命令和结果
  • 下一步行动:明确的后续步骤和条件

符合规范:"对于复杂工作,贡献者必须在 ai-plan/public/<topic>/traces/ 下维护匹配的执行追踪,记录当前日期、关键决策、验证里程碑和下一步行动。"


📝 Walkthrough

总体说明

此PR更新了多个README和中文文档,将具体的文件路径引用替换为接口/类型名称,调整导航文本措辞,并移除过时的内部实现细节参考,不涉及代码逻辑改动。

变更详情

内聚体 / 文件 摘要
模块README文档
GFramework.Cqrs.Abstractions/README.md, GFramework.Godot/README.md, GFramework.SourceGenerators.Common/README.md
将"子系统地图"和文档说明中的具体文件路径引用(如Cqrs/*)替换为泛型接口/类型名称(如IRequest<TResponse>ICommand<,>),或用更通用的描述替换特定实现标记。
治理文档与跟踪
ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md, ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md
更新文档覆盖治理工作流程:从RP-048迁移到RP-050,记录批量验证脚本、构建命令结果,并调整后续批处理的风险评估标记。
中文文档导航和措辞
docs/zh-CN/core/index.md, docs/zh-CN/godot/index.md, docs/zh-CN/game/*.md, docs/zh-CN/godot/*.md
统一更新导航指引文本,将"优先看""转到"改为"继续阅读";移除特定实现参考(如ai-libs路径、CoreGrid具体引用);调整跨文档引用的条件措辞;更新字段说明文本(如EnableStatisticsDataRepository等)。
工具文档链接标签
tools/gframework-config-tool/README.md
更新"Documentation"部分的两个现有文档链接的显示标签,URL/路径保持不变。

评估代码审查工作量

🎯 1 (Trivial) | ⏱️ ~8 minutes

可能相关的PR

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive 标题 "Docs/sdk update documentation" 与实际变更内容部分相关,但过于宽泛且缺乏具体性。变更涉及多个文档更新(包括游戏、Godot、CQRS、源代码生成器等模块的README和文档),但标题未能准确反映主要变更的具体性质(即调整文档措辞、移除内部路径引用、更新导读文本等)。 建议优化标题为更具体的表述,如 "Update documentation wording and remove internal path references" 或 "Refactor documentation cross-links and reader-facing labels",以更清晰地反映本次变更的核心目的。
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/sdk-update-documentation

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Apr 29, 2026

Copy link
Copy Markdown

Greptile Summary

This PR is a documentation-only cleanup across 18 files, removing internal/governance-facing language from reader-facing docs. Changes consistently apply the documentation rules from AGENTS.md: replacing imperative navigation prompts ("转到", "优先看", "应该回到") with neutral phrasing ("可继续阅读"), removing references to internal artifacts (ai-libs/, CoreGrid), eliminating "旧文档" references, and converting raw file-path listings to type-level API references in READMEs. The ai-plan/ tracking and trace files are updated to reflect the new recovery points and batch status.

Confidence Score: 5/5

Safe to merge — documentation-only changes with no code, API, or behavioral modifications.

All 18 changed files are documentation or internal AI-plan tracking. Every edit follows the AGENTS.md documentation rules (removing raw paths, internal governance language, and imperative navigation prompts). No code, tests, or package metadata are affected. Validations recorded in the trace all passed.

No files require special attention.

Important Files Changed

Filename Overview
GFramework.Cqrs.Abstractions/README.md Interface listings replaced with type-level generic names (e.g., IRequest<TResponse>) instead of raw source file paths — aligns with AGENTS.md requirement to avoid surfacing raw filenames as navigation text.
GFramework.Godot/README.md Removed raw test file path from reader-facing text, keeping only the factual statement about the tested boundary.
GFramework.SourceGenerators.Common/README.md Replaced IsPackable=false implementation detail with reader-facing installation guidance, removing a build-property term that would be opaque to NuGet consumers.
docs/zh-CN/godot/ui.md Replaced internal "CoreGrid" project-specific references with generic reader-facing phrasing; removed "真实消费者 wiring" governance language.
docs/zh-CN/godot/signal.md Removed "旧文档" reference and migration chain framing; simplified boundary section to state the current public API entry point directly.
ai-plan/public/documentation-full-coverage-governance/todos/documentation-full-coverage-governance-tracking.md Recovery point advanced to RP-050; status summary and next steps updated to reflect the upstream branch being gone and the new origin/main baseline strategy.
ai-plan/public/documentation-full-coverage-governance/traces/documentation-full-coverage-governance-trace.md New RP-049 and RP-050 trace sections added with decisions, validation results, and next steps for the two batch rounds performed on 2026-04-29.
tools/gframework-config-tool/README.md Raw file path labels in the Documentation section replaced with Chinese reader-facing titles ("Game 配置工具", "Game 配置系统").

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Docs/sdk update documentation] --> B[README cleanups]
    A --> C[docs/zh-CN page cleanups]
    A --> D[ai-plan tracking updates]

    B --> B1[GFramework.Cqrs.Abstractions/README.md\nFile paths to type-level API names]
    B --> B2[GFramework.Godot/README.md\nRemove raw test path reference]
    B --> B3[GFramework.SourceGenerators.Common/README.md\nIsPackable detail to reader-facing install note]
    B --> B4[tools/gframework-config-tool/README.md\nRaw path labels to semantic titles]

    C --> C1[godot/ui.md\nRemove CoreGrid internal refs]
    C --> C2[godot/signal.md\nRemove old-docs refs]
    C --> C3[godot/storage, setting, logging, index\nReplace imperative nav with neutral phrasing]
    C --> C4[game/data, storage, scene, config-system\nRemove internal path and governance refs]
    C --> C5[core/index.md, ecs/arch.md\nNeutral navigation language]

    D --> D1[todos tracking\nRP-048 to RP-050]
    D --> D2[traces\nAdd RP-049 and RP-050 entries]
Loading

Reviews (1): Last reviewed commit: "docs(documentation-governance): 收口数据与 UI..." | Re-trigger Greptile

@github-actions

Copy link
Copy Markdown

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
2181    ↑22 2181    ↑22 0 0 0 0 35.3s    ↓593ms

Test Results

passed 2181 passed ↑22

Details

tests 2181 tests ↑22
clock 35.3s ↓593ms
tool nunit
build CI - Build & Test arrow-right build-and-test link #1012
pull-request Docs/sdk update documentation link #303

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2148 0 0 5.4s

build-and-test: Run #1012

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Pending ⏳ Other ❓ Flaky 🍂 Duration ⏱️
2181 2181 0 0 0 0 0 35.3s

🎉 All tests passed!

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
Does_Not_Report_When_FieldInjectedModel_Is_Registered 38 2.3s 5.4s
SendRequestAsync_Should_ResolveCqrsRuntime_OnlyOnce_When_AccessedConcurrently 38 4.2s 4.8s
Generates_Scene_Behavior_Boilerplate 38 2.0s 4.6s
Context_Caching_Should_Improve_Performance 38 799ms 1.1s
CleanupDuringAcquire_Should_NotCauseRaceCondition 38 1.1s 1.1s
Append_ShouldNotBlock 38 1.0s 1.0s
RegisterCqrsHandlersFromAssembly_Should_Deduplicate_Repeated_Assembly_Registration 38 223ms 791ms
ConfigModuleCanRunDuringArchitectureInitialization 38 210ms 550ms
PendingCount_ShouldReflectQueuedEntries 38 501ms 501ms
Cleanup_Should_NotRemoveActiveLocks 38 404ms 406ms

± Comparison with run #1002 at df49d26 | 🎉 No failed tests detected across all runs. | 🍂 No flaky tests detected across all runs. | ⏱️ Measured over 38 runs.

Github Test Reporter by CTRF 💚

@github-actions

Copy link
Copy Markdown

MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ REPOSITORY gitleaks yes no no 3.79s
✅ REPOSITORY trufflehog yes no no 3.93s

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@GeWuYou

GeWuYou commented Apr 29, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@GeWuYou

GeWuYou commented Apr 29, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@GeWuYou GeWuYou merged commit 79f9cb3 into main Apr 29, 2026
7 checks passed
@GeWuYou GeWuYou deleted the docs/sdk-update-documentation branch April 29, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant